corpus: rebuild manifest surfaces from all three blocks — fixes the MANIFEST_ERROR my #9 merge shipped - #10
Merged
Conversation
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_3bc1db60-0e43-4df0-ac46-b80f40b58659) |
…ANIFEST_ERROR my #9 merge shipped The #9 mirror rebuilt semantic_surface/excluded from the counts block alone, dropping relations.IFCRELFILLSELEMENT and storeys.IFCBUILDINGSTOREY, and I merged it while both verdict jobs were red — the gate said MANIFEST_ERROR and was right. The mirror now folds the relations and storeys blocks into the declared surface/exclusions; both verdicts PASS locally against the committed observations and the index re-chains.
DrunkOnJava
force-pushed
the
corpus/fix-manifest-surface
branch
from
August 30, 2026 23:29
0928ea2 to
ad2421c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The #9 mirror rebuilt semantic_surface/excluded from the counts block
alone, dropping relations.IFCRELFILLSELEMENT and storeys.IFCBUILDINGSTOREY,
and I merged it while both verdict jobs were red — the gate said
MANIFEST_ERROR and was right. The mirror now folds the relations and
storeys blocks into the declared surface/exclusions; both verdicts PASS
locally against the committed observations and the index re-chains.
Note
Low Risk
Metadata-only corpus manifest and index updates; no runtime decoder or auth changes, only restores CI gate consistency.
Overview
Repairs corpus manifests after a mirror rebuild that only derived
semantic_surface/excludedfromcounts, which leftrelations.opening_fillsandstoreys.building_storeysout of sync with the normative §6.1 blocks and trippedMANIFEST_ERRORintools/verdict.py.On g-2026-0002 (full export),
relations.opening_fillsandstoreys.building_storeysare added to the claimed surface. On g-2026-0001 (element fixture),storeys.building_storeysis claimed andrelations.opening_fillsis listed underexcludedasdecoder_baseline, matching the existing relation row. Redundantrelation_ifc_type/expected_pairsandstorey_ifc_type/expected_storeysfields are removed from those blocks per corpus README.MANIFEST_INDEX.jsonmanifest hashes,prev_hash, andchain_headare updated for the re-chained manifests.Reviewed by Cursor Bugbot for commit 0928ea2. Configure here.